-
Notifications
You must be signed in to change notification settings - Fork 9.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for elasticsearch outbound connection and relevant accepter #22988
Add support for elasticsearch outbound connection and relevant accepter #22988
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Welcome @Symbianx 👋
It looks like this is your first Pull Request submission to the Terraform AWS Provider! If you haven’t already done so please make sure you have checked out our CONTRIBUTING guide and FAQ to make sure your contribution is adhering to best practice and has all the necessary elements in place for a successful approval.
Also take a look at our FAQ which details how we prioritize Pull Requests for inclusion.
Thanks again, and welcome to the community! 😃
@justinretzolk I see you added a |
Hey @Symbianx 👋 Thank you for checking in on this, and thank you for your contribution! I was actually removing the Unfortunately, I'm not able to provide an estimate on when this will be reviewed due to the potential of shifting priorities (we prioritize work by count of ":+1:" reactions, as well as a few other things). A larger prioritization document is in the works, but in the meantime additional information may be found in the FAQ. Outside of that, as soon as time permits, one of the engineers on the team will work on a full review so that we can get this merged in 🙂. |
c0e59e9
to
ca6abcc
Compare
ca6abcc
to
f1c6ff6
Compare
Just rebased this PR with master which should make it easier to review |
Hey @justinretzolk , sorry to bother you again. This PR has been here for quite a while and I know you have a lot more PRs and issues to look at so I have one simple query. Is there a known way for us to hook into the provider lifecycle to add our own resources/extensions without having to fork and build the whole repo? Cloudformation doesn't support cross-cluster search either so the fact that we can't configure this via code in any way is really setting us back. |
Hey @Symbianx 👋 No bother at all! That's what I'm here for, and I very much appreciate your understanding regarding prioritization 🙂. The best way to be able to incorporate changes like this prior to them being merged in would indeed be to build the provider from source. Given that you've got a fork and the proposed change written, you could build and use a developer version of the provider using the steps outlined in the development environment setup documentation (which is further detailed in the Development Overrides for Provider Developers documentation). I would recommend that if you decide to go this route, you only use this development version of the provider for the exact resources you need it for, so that you don't have too much work to move back to the main provider once the resources have been added (you'll need to do some |
Hey @Symbianx, Great job you did on this issue! I would love to help out with the feedback @justinretzolk gave, but unfortunately I'm quite new to the "building an AWS provider" world. |
@riy Heya |
…nection_accepter resources
f1c6ff6
to
a314303
Compare
…ck if resource is new
943362a
to
59f43bc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🎉
$ make testacc PKG=opensearch TESTS="TestAccOpenSearchOutboundConnection_|TestAccOpenSearchInboundConnectionAccepter_"
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/opensearch/... -v -count 1 -parallel 20 -run='TestAccOpenSearchOutboundConnection_|TestAccOpenSearchInboundConnectionAccepter_' -timeout 180m
=== RUN TestAccOpenSearchInboundConnectionAccepter_basic
=== PAUSE TestAccOpenSearchInboundConnectionAccepter_basic
=== RUN TestAccOpenSearchInboundConnectionAccepter_disappears
=== PAUSE TestAccOpenSearchInboundConnectionAccepter_disappears
=== RUN TestAccOpenSearchOutboundConnection_basic
=== PAUSE TestAccOpenSearchOutboundConnection_basic
=== RUN TestAccOpenSearchOutboundConnection_disappears
=== PAUSE TestAccOpenSearchOutboundConnection_disappears
=== CONT TestAccOpenSearchInboundConnectionAccepter_basic
=== CONT TestAccOpenSearchOutboundConnection_basic
=== CONT TestAccOpenSearchOutboundConnection_disappears
=== CONT TestAccOpenSearchInboundConnectionAccepter_disappears
--- PASS: TestAccOpenSearchOutboundConnection_disappears (1622.82s)
--- PASS: TestAccOpenSearchOutboundConnection_basic (1636.86s)
--- PASS: TestAccOpenSearchInboundConnectionAccepter_disappears (1803.42s)
--- PASS: TestAccOpenSearchInboundConnectionAccepter_basic (1877.88s)
PASS
ok github.com/hashicorp/terraform-provider-aws/internal/service/opensearch 1880.647s
Hey @Symbianx, thanks for your contribution! 👏 👏 This was in great shape, I just made a few small adjustments:
|
This functionality has been released in v4.40.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
Hey @Symbianx Is it possible to import inbound connection in a different region then of the local opensearch?
|
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Community Note
Closes #13609
Output from acceptance testing: